Please refer to RP-213700 for detailed scope of the SI.
R1-2203236 Work plan for NR network-controlled repeaters ZTE
R1-2203235 TR skeleton for NR network-controlled repeaters ZTE
[109-e-R18-Repeater-01] – Nan (ZTE)
Email discussion and approval of TR skeleton for Rel-18 SI on NR network-controlled repeaters by May 13
R1-2205231 TR 38.867 skeleton for Study on NR network-controlled repeaters Rapporteur (ZTE)
Decision: As per email decision posted on May 16th,
Agreement
The TR skeleton in R1-2205231 for TR 38.867 Study on NR network-controlled repeaters is endorsed as v0.0.0.
Note: Cost analysis on network controlled repeaters can be captured in the annex pending RAN1 consensus.
Updated TR including the latest progress in this meeting in:
R1-2205496 TR 38.867 v0.1.0 for Study on NR network-controlled repeaters Rapporteur (ZTE)
Decision: As per email decision posted on May 20th, v0.1.0 is endorsed.
R1-2203237 Discussion on side control information to enable NR network-controlled repeaters ZTE
Proposal 1: Recommend to capture the conceptual model of network-controlled repeater (as shown in Figure 1) in TR.
Proposal 2: The side control information is only targeted to control the behavior of forwarding link (F-link).
Proposal 3: The indication of TDD UL-DL configuration to NCR in semi-static/static way is recommended.
Proposal 4: TDD UL-DL configuration dedicated to NCR is not necessary.
Proposal 5: The legacy mechanism for DL synchronization by detecting the SSB is applicable for NCR.
Proposal 6: The following timing alignment is proposed for NCR, and no additional spec impact is expected.
‐ NCR C-link: its DL Rx timing (C1) and UL Tx timing (C2) can be determined as for a “UE”.
‐ NCR F-link: ideally, the same timing as NCR C-link is expected
• F-link DL Rx timing (F1) = C-link DL Rx timing (C1)
• F-link DL Tx timing (F3) = F-link DL Rx timing (F1)
• F-link UL Tx timing (F2) = C-link UL Tx timing (C2)
• F-link UL Rx timing (F4) = F-link UL Tx timing (F2)
Proposal 7: The resource multiplexing between the C-link and F-link can be managed by the gNB without additional specification impact.
Proposal 8: The beam indication for the C-link 1&2 can be reused by the F-link 1&2 to ensure the same channel condition of control signaling and backhaul forwarding without extra signaling cost.
Proposal 9: To enable the forwarding of common channel, the beam information can be achieved in static or semi-static way by:
• Configuring the mapping relationship between DL/UL common signal and the NCR’s beams
• Indicating the beam information along with the applicable time instant directly
Proposal 10: To enable the forwarding of UE dedicated channel in dynamic way, the beam information can be achieved by:
• Indicating the beam information along with the applicable time domain resource directly
• Using enhanced TCI with the logic beam index allocated per NCR’s beam
Proposal 11: Beam information is beneficial and recommended as the side control information for network-controlled repeater to improve the performance.
Proposal 12: ON-OFF information is beneficial and recommended as the side control information for network-controlled repeater for both energy efficiency and interference management.
Proposal 13: Support at least large time scale ON-OFF configuration on the whole forwarding link for NCR.
Proposal 14: Finer granularity of ON-OFF information, e.g. slot level and link level configuration, can also be considered for NCR forwarding links.
Proposal 15: Power control information can be applicable for both UL and DL forwarding links.
Proposal 16: To enable the power controlling of the output power of NetConRep-RU, the indication of maximum Tx power or amplified gain can be considered as part of side control information.
Proposal 17: Long term based power control can be considered for NCR forwarding links.
Decision: The document is noted.
R1-2203133 Discussion on side control information to enable NR network-controlled repeaters Huawei, HiSilicon
R1-2203343 Discussion on side control information to enable NR network-controlled repeaters Spreadtrum Communications
R1-2203354 Discussion on side control information to enable NR network-controlled repeaters Nokia, Nokia Shanghai Bell
R1-2203376 Discussions on side control information to enable NR network-controlled repeaters InterDigital, Inc.
R1-2203476 Discussion on side control information for NR network-controlled repeaters CATT
R1-2203578 Discussion on side control information to enable NR network-controlled repeaters vivo
R1-2203697 Discussion on side control information for network-controlled repeaters NEC
R1-2203741 Considerations on side control information to enable NR network-controlled repeaters Sony
R1-2203832 Discussion on side control information to enable NR network-controlled repeaters xiaomi
R1-2203921 Side control information to enable NR network-controlled repeaters Samsung
R1-2204064 Discussion on side control information for network controllable repeater Lenovo
R1-2204066 Side Control Information for Network-Controlled Repeaters Charter Communications, Inc
R1-2204086 Side Control Information for supporting initial access CableLabs
R1-2204119 Side control information for network-controlled repeaters SHARP Corporation
R1-2204258 Potential side control information for NW-controlled repeater Apple
R1-2204321 Discussion on Side control information to enable NR network-controlled repeaters CMCC
R1-2204393 Discussion on side control information to enable NR network-controlled repeaters NTT DOCOMO, INC.
R1-2204532 Discussion on side control information for NCR LG Electronics
R1-2204565 Discussion on side control signals for network-controlled repeaters Panasonic
R1-2204610 Discussion on side control information to enable NR network-controlled repeaters CAICT
R1-2204642 Control information for enabling NW-controlled repeaters Ericsson
R1-2204653 Discussions on side control information for network-controlled repeater ETRI
R1-2204688 Side control information for network-controlled repeaters MediaTek Inc.
R1-2204757 Discussion on Side control information to enable NR network-controlled repeaters CEWiT, IITK
R1-2204813 Discussion on Side control information to enable NR network-controlled repeater Intel Corporation
R1-2204847 Discussion on side control information to enable NR network-controlled repeaters KDDI Corporation
R1-2204864 Side control information to enable NR network-controlled repeaters AT&T
R1-2205047 On side control information for network controlled repeaters (NCR) Qualcomm Incorporated
R1-2205068 Initial view on Network-controlled repeater Rakuten Mobile
R1-2205085 Side control information for NR network-controlled repeaters Fujitsu Limited
//This one is to use NWM – please use RAN1-109-e-NWM-R18-Repeater-02 as the document name
Note this thread was conducted over email reflector, not NWM
[109-e-R18-Repeater-02] – Nan (ZTE)
Email discussion on side control information by May 20
- Check points: May 13, May 20
R1-2205233 Summary#1 of Email discussion on side control information Moderator (ZTE)
From May 12th GTW session
Agreement
Capture the following model of network-controlled repeater in TR 38.867.
· The NCR-MT is defined as a function entity to communicate with a gNB via Control link (C-link) to enable the information exchanges (e.g. side control information). The C-link is based on NR Uu interface.
o Note: Side control information is at least for the control of NCR-Fwd
· The NCR-Fwd is defined as a function entity to perform the amplify-and-forwarding of UL/DL RF signal between gNB and UE via backhaul link and access link. The behavior of the NCR-Fwd will be controlled according to the received side control information from gNB.
Agreement
At least for FR2, beam information is beneficial and recommended as the side control information for network-controlled repeater to control the behaviour of NCR at least for access link
· FFS: Detailed mechanism of indication.
· Note: There are no supporting evaluation results on FR1 at this point to reach similar conclusion
Decision: As per email decision posted on May 14th,
Agreement
Both fixed beam and adaptive beam can be considered at NCR for both C-link and backhaul-link.
· FFS: the mechanism for indication and determination of beam.
· Note: Fixed beam refers to the case that beam at NCR for both C-link and backhaul-link cannot be changed.
Agreement
For the TDD UL/DL configuration of network controller repeater:
· At least semi-static TDD UL/DL configuration is needed for network-controlled repeater for links including C-link, backhaul link and access link.
o FFS: handling of flexible symbols
· Note1: The same TDD UL/DL configuration is always assumed for backhaul link and access link
· Note2: The same TDD UL/DL configuration is assumed for C-link and backhaul link and access link if NCR-MT and NCR-Fwd are in the same frequency band.
Agreement
For the timing of NCR, the following assumption is considered as baseline:
· The DL receiving timing of the NCR-Fwd is aligned with the DL receiving timing of the NCR-MT.
· The UL transmitting timing of the NCR-Fwd is aligned with the UL transmitting timing of the NCR-MT.
· FFS: the impact of internal delay on the following timing relationships:
o The DL receiving timing and DL transmitting timing of the NCR-Fwd
o The UL transmitting timing and UL receiving timing of the NCR-Fwd
Decision: As per email decision posted on May 17th,
Agreement
ON-OFF information is beneficial and recommended for network-controlled repeater to control the behaviour of NCR-Fwd.
· FFS: Detailed mechanism of ON-OFF indication and determination
· FFS: explicit indication or implicit indication of ON-OFF information
Agreement
Both the dynamic indication and semi-static indication can be considered for the beam of access link for NCR-Fwd.
· FFS: the details of each indication
· FFS: the maximum number of beams configured for NCR-Fwd access link
R1-2205340 Summary#2 of Email discussion on side control information Moderator (ZTE)
R1-2205495 Summary#3 of Email discussion on side control information Moderator (ZTE)
From May 19th GTW session
Agreement:
The following options can be considered to indicate the ON-OFF information from gNB to NCR for controlling the behaviour of NCR-Fwd:
· Option 1: Explicit indication with on-off state (e.g., via dynamic or semi-static signalling) or on-off pattern (e.g., periodic/semi-static ON-OFF pattern or new DRX-like pattern for ON-OFF)
· Option 2: Implicit indication via the signalling for other information (e.g., beam, DL/UL configuration, or PC information)
o Note: This example does not imply that PC information is necessary or not.
· Other solutions (e.g., potential combination of explicit and implication solution) can be further discussed.
Agreement:
Capture the following assumption of network-controlled repeater in TR 38.867.
· At least one of the NCR-MT’s carrier(s) should be within the set of carriers forwarded by the NCR-Fwd in same frequency range.
o The NCR-MT and NCR-Fwd operating in the same carrier is prioritized for the study.
Agreement:
Capture the following assumption of network-controlled repeater in TR 38.867.
· As baseline, same large-scale properties of the channel, i.e., channel properties in Type-A and Type-D (if applicable), are expected to be experienced by C-link and backhaul link (at least when the NCR-MT and NCR-Fwd operating in same carrier).
Agreement:
As baseline, the same TCI states as C-link are assumed for beam at NCR-Fwd for backhaul link if the NCR-MT’s carrier(s) is within the set of carriers forwarded by the NCR-Fwd.
· FFS: additional indication from gNB to determine the beam at NCR-Fwd for backhaul link or implicit determination of the beam at NCR-Fwd for backhaul link
Note: the same assumption of the beam correspondence is applied for DL/UL of the backhaul link at NCR-Fwd as the DL/UL of the C-link at NCR-MT.
Agreement:
The beam correspondence is assumed for:
· the DL/UL of the access link at NCR-Fwd
Decision: As per email decision posted on May 24th,
Agreement
Recommend to capture the following observation in TR 38.867:
· The benefits of power information used to control the behavior of NCR-Fwd for the DL of access link and/or UL of backhaul link are observed by the following inputs:
o [Source-1, Huawei] shows that for the uplink transmission via NCR, a fixed NCR amplifying gain may lead to interference to the gNB or NCR UL coverage loss. For the downlink transmission via NCR, a fixed NCR amplifying gain may lead to NCR RU saturation or NCR DL coverage loss.
o [Source-2, vivo] shows that the optimal system performance can be achieved when repeater’s gain is set to a proper value.
o [Source-3, ETRI] shows that dynamic repeater gain/power control can provide additional SINR gain over semi-static repeater gain/power configuration.
o [Source-4, Ericsson] mentions that the gain control is needed for self-interference management due to repeater oscillation.
· This agreement does not change the prioritization of PC
Agreement
The controlling of the amplifying gain of NCR-Fwd is considered to enable the power control of NCR-Fwd if PC is recommended as side control information for NCR in Rel-18
· FFS: Controlling of the transmission power of NCR-Fwd
Agreement
Recommend to capture the following examples of the transmission/reception of C-link and backhaul link by NCR in TR 38.867.
· The DL of C-link and DL of backhaul link can be performed simultaneously or in TDM way.
· The UL of C-link and UL of backhaul link can be performed in TDM way
· Note-1: Multiplexing is under the control of gNB with consideration for NCR capability
· Note-2: Simultaneous transmission of the UL of C-link and UL of backhaul link is subject to NCR’s capability
R1-2205048 On L1-L2 signaling for side control information for NCR Qualcomm Incorporated
· Proposal 1: Support dynamic and granular (symbol-level) side control info indication.
· Proposal 2: At least, support L1 (DCI-based) signaling to carry side control info. RAN1 to also discuss L2/L3 (MAC-CE or RRC based) signaling to carry side control info associated with forwarding semi-static/periodic signals (such as SSB/RMSI/CSI-RS/RACH/etc.)
· Proposal 3: The signaling that carries the side control info should also indicate the associated time-domain resources (e.g., symbol/slot indices) within which the repeater is to adopt the indicated side control info.
· Proposal 4: NCR-UE’s features/capabilities should be discussed later, after discussing/deciding about the architecture.
· Proposal 5: Support indication of A&F specific information to the network.
o At least including beam-relate info (e.g., the number of supported TX/RX beams)
o FFS: indication of other information such as power-related and/or frequency-related info.
o FFS: signaling method (e.g., new L1/L2 signaling, or L3 signaling with a possibility of joint report with other repeater’s features/capabilities associated with NCR-UE)
Decision: The document is noted.
R1-2203134 Discussion on L1/L2 signaling for side control information Huawei, HiSilicon
R1-2203238 Discussion on L1/L2 signaling for side control information ZTE
R1-2203355 Discussion on L1/L2 signaling for side control information of network-controlled repeaters Nokia, Nokia Shanghai Bell
R1-2203377 Discussion on L1/L2 signaling for side control information InterDigital, Inc.
R1-2203477 Discussion on signalling of side control informaion for NR network-controlled repeaters CATT
R1-2203579 Discussion on signaling for side control information vivo
R1-2203698 Discussion on signaling for side control information NEC
R1-2203742 Considerations on L1/L2 signaling for side control information Sony
R1-2203833 Discussion on L1/L2 signalling for side control information xiaomi
R1-2203922 L1/L2 signaling for side control information Samsung
R1-2204065 Discussion on L1/L2 signaling for side control information of network-controlled repeaters Lenovo
R1-2204259 Discussion on L1/L2 signaling for side control information Apple
R1-2204322 Discussion on L1/L2 signaling for side control information CMCC
R1-2204394 Discussion on L1/L2 signaling for side control information NTT DOCOMO, INC.
R1-2204533 Discussion on L1/L2 signaling for side control information LG Electronics
R1-2204643 Signaling of control information for NW-controlled repeaters Ericsson
R1-2204654 Discussions on L1/L2 signaling for side control information ETRI
R1-2204689 L1/L2 control signaling for enabling network controlled repeaters MediaTek Inc.
R1-2204758 Discussion on L1/L2 signaling for side control information for NCR CEWiT, IITK
R1-2204814 Discussion on L1/L2 signaling for side control information Intel Corporation
R1-2204848 Discussion on L1/L2 signaling for side control information KDDI Corporation
R1-2205069 Initial view on signaling for Network-controlled repeater Rakuten Mobile
R1-2205086 NR network-controlled repeaters receive signaling of side control information Fujitsu Limited
[109-e-R18-Repeater-03] – Lei (Fujitsu)
Email discussion on L1/L2 signaling for side control information by May 20
- Check points: May 13, May 20
R1-2205237 Summary#1 on L1/L2 signaling for side control information Moderator (Fujitsu)
From May 12th GTW session
Agreement
The NCR-MT can obtain the necessary configuration for receiving the L1/L2 signaling of the side control information.
· Option 1: The necessary configuration is from RRC.
· Option 2: The necessary configuration is from OAM or hard-coded.
· Option 3: The necessary configuration is partially configured by RRC and partially configured by OAM or hard-coded.
Decision: As per email decision posted on May 14th,
Agreement
For indication of NCR-Fwd ON-OFF for efficient interference management and improved energy efficiency, both dynamic and semi-static indication can be considered
· FFS: RAN1 to consider whether/how to handle the forwarding of broadcast and cell-specific signals/channels.
Agreement
From the perspective of signaling design, following mechanisms can be considered for the access link beamforming of the NCR-Fwd.
· Option #2-1: Dynamic beam indication only
· Option #2-2: Semi-static beam indication only
· Option #2-3: Dynamic beam indication and semi-static beam indication
Decision: As per email decision posted on May 16th,
Agreement
For an NCR-MT, the necessary configurations from RRC and/or OAM(or hard-coded) contain:
· The configurations of PHY channels to carry the L1/L2 signaling:
o The configurations for receiving PDCCH and PDSCH.
o The configurations for transmitting PUCCH, if needed.
o The configurations for transmitting PUSCH, if needed.
· The configurations of L1/L2 signaling:
o The configurations for DCI.
o The configurations for UCI, if needed.
o The configurations for MAC CE, if needed.
R1-2205456 Summary#2 on L1/L2 signaling for side control information Moderator (Fujitsu) (rev of R1-2205386)
From May 17th GTW session
Agreement
In the access link beam indication, an access link beam can be indicated by:
RAN1 to select one of the two options, combine the two options, or select both options in RAN1#110
Conclusion
Legacy UE mechanism is sufficient to achieve DL/UL timing for NCR-MT
R1-2205519 Summary#3 on L1/L2 signaling for side control information Moderator (Fujitsu)
From May 19th GTW session
Agreement
For the parameters in the necessary configurations for L1/L2 signaling, the existing parameters for PDCCH, PDSCH, PUCCH, PUSCH, DCI, UCI and MAC CE in Rel-17 are the baseline for further discussion.
· Note 1: This does not imply that all Rel-17 parameters will be supported for the NCR-MT.
· Note 2: This does not imply that PUCCH, PUSCH, UCI and MAC CE are currently agreed to be supported. Further consideration is needed.
Decision: As per email decision posted on May 24th,
Agreement
For the signaling of information on UL-DL TDD configuration, if the NCR-MT can acquire the TDD configuration as legacy UEs or from the OAM, new signaling may not be necessary.
· Note 1: The same TDD UL/DL configuration is assumed for C-link and backhaul link and access link if the NCR-MT and the NCR-Fwd are in the same frequency band.
· FFS: Other cases where new signaling may be necessary.
Agreement
For the signaling of the side control information of timing to align transmission / reception boundaries, new signaling may be unnecessary.
· FFS: the impact of internal delay
Agreement
The time at which the NCR applies an access link beam indication should be considered.
Agreement
As for the time-domain granularity of the access link beam indication, one or both of the following options can be considered:
· Option 1: slot-level
· Option 2: symbol-level
· FFS: The details of indication signaling
R1-2203239 Discussion on other issues for NR network-controlled repeater ZTE
R1-2203580 Discussion on in-band repeater vivo
R1-2204067 Deployment Scenarios for Network-Controlled Repeaters Charter Communications, Inc
R1-2204534 Discussion on operation scenarios for NCR LG Electronics
R1-2204644 Terminology for NW-controlled repeaters Ericsson
R1-2204930 Other considerations for NR network-controlled repeaters Huawei, HiSilicon
Please refer to RP-221229 for detailed scope of the SI.
[110-R18-NWC_Repeater] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Nan (ZTE)
R1-2206017 Updated TR38.867 for Study on NR NCR ZTE
R1-2208191 TR 38.867 v0.2.0 for Study on NR network-controlled repeaters Rapporteur (ZTE)
From Thursday session
Agreement
· The following TP is agreed as the conclusion for the TR on NWC repeater for RAN1.
|
RAN1 has studied the side control information for NCR with corresponding signalling (including its configuration). The following are recommended to be specified as part of Rel-18 NCR WI from RAN1’s perspective: - Beam information as side control information - ON-OFF information as side control information - UL-DL TDD configuration and NCR’s behaviour over flexible symbols. |
R1-2205813 Power Control and Side Control Information for NCRs Pivotal Commware, AT&T
R1-2205875 On the side control information and performance evaluation for NCR Huawei, HiSilicon
R1-2205939 Discussion on side control information to enable NR network-controlled repeaters Nokia, Nokia Shanghai Bell
R1-2206001 Discussion on side control information to enable NR network-controlled repeaters Spreadtrum Communications
R1-2206018 Discussion on side control information for NCR ZTE
R1-2206055 Discussion on side control information to enable NR network-controlled repeaters vivo
R1-2206128 Additional considerations on side control information to enable NR network-controlled repeaters Sony
R1-2206174 Discussion on side control information for NR network-controlled repeaters Fujitsu
R1-2206183 Discussions on side control information for NR network-controlled repeaters InterDigital, Inc.
R1-2206208 Side control information for network-controlled repeaters NICT and Toyota InfoTechnology Center
R1-2206330 Discussion on side control information for NCR OPPO
R1-2206413 Side control information to enable NR network-controlled repeaters CATT
R1-2206435 Discussion on side control information for network-controlled repeaters Panasonic
R1-2206478 Discussion on side control information to enable NR network-controlled repeaters NEC
R1-2206597 Discussion on Side control information to enable NR network-controlled repeater Intel Corporation
R1-2206656 Discussion on side control information to enable NR network-controlled repeaters Xiaomi
R1-2206698 Discussion on side control information for network-controlled repeaters China Telecom
R1-2206840 Side control information to enable NR network-controlled repeaters Samsung
R1-2206927 Discussion on side control information to enable NR network-controlled repeaters CMCC
R1-2206957 Discussion on side control information for network-controlled repeater ETRI
R1-2206981 Side control information for network-controlled repeaters MediaTek Inc.
R1-2207075 Discussion on Side control information to enable NR network-controlled repeaters CEWiT, IITK
R1-2207120 Discussion on side control information for NCR Rakuten Mobile, Inc
R1-2207127 Discussion on side control information to enable NCR operations Sharp
R1-2207247 On side control information for network controlled repeaters (NCR) Qualcomm Incorporated
R1-2207297 Discussion on side control information for network-controlled repeater Lenovo
R1-2207300 Discussion on side control information to enable NR network-controlled repeaters CAICT
R1-2207345 Discussion on side control information for NR network-controlled repeaters Apple
R1-2207366 Discussion on side control information for NCR LG Electronics
R1-2207420 Discussion on side control information to enable NR network-controlled repeaters NTT DOCOMO, INC.
R1-2207460 Discussion on side control information to enable NR network-controlled repeaters KDDI Corporation
R1-2207680 Control information for enabling NCR Ericsson
R1-2207688 Summary#1 of discussion on side control information Moderator (ZTE)
From Monday session
Agreement:
The time domain resource corresponding to an access link beam can be determined with following options:
· Option 1: Explicit determination based on the explicitly indicated the time domain resources per beam indication
Note-1: Different parameters may be indicated for semi-static or dynamic beam indication
Note 2: One or multiple beams can be indicated via single beam indication.
Agreement:
For the timing of NCR, the following assumption is captured into TR 38.867.
· The DL transmitting timing of the NCR-Fwd is delayed after the DL receiving timing of the NCR-MT (or the NCR-Fwd) by the internal delay;
· The UL receiving timing of the NCR-Fwd is advanced before the UL transmitting timing of the NCR-MT (or the NCR-Fwd) by the internal delay.
R1-2207933 Summary#2 of discussion on side control information Moderator (ZTE)
From Wed session
Agreement:
The NCR-Fwd is always expected to be “OFF” unless otherwise explicitly or implicitly indicated by gNB.
· Note-1: This applies to the case regardless of the RRC state of NCR-MT.
· Note-2: Indication (e.g., received when NCR-MT in RRC-connected) or DRX state of NCR-MT to control the ON-OFF behaviour of NCR-Fwd when the NCR-MT is in RRC-idle/inactive is not precluded.
The above is not meant to imply any signalling design for NCR-Fwd ON-OFF.
R1-2208041 Summary#3 of discussion on side control information Moderator (ZTE)
Agreement
For the flexible symbol based on the semi-static configuration (e.g., TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated), following options are considered for the NCR-Fwd on these symbols
· Option 1: The NCR-Fwd is expected to be OFF or not forwarding over these symbols
· Option 2: The NCR-Fwd will follow the TDD operation determined by NCR-MT, i.e., determined by NCR-MT based on the received SFI indication or scheduling from gNB
o Note: It means that no new side control signalling is needed.
· Option 3: The NCR-Fwd will follow a new dynamic side control signalling of DL/UL forwarding over these symbols to NCR-Fwd
Final summary in R1-2208192.
R1-2205876 On L1/L2 signaling for side control information Huawei, HiSilicon
R1-2205940 Discussion on L1/L2 signaling for side control information of network-controlled repeaters Nokia, Nokia Shanghai Bell
R1-2206002 Discussion on L1/L2 signaling for side control information Spreadtrum Communications
R1-2206019 Discussion on L1/L2 signaling for side control information ZTE
R1-2206056 Discussion on signaling for side control information vivo
R1-2206129 Additional considerations on L1/L2 signaling for side control information Sony
R1-2206175 Discussion on L1/L2 signaling for side control information Fujitsu
R1-2206184 L1/L2 signaling for side control information of network-controlled repeaters InterDigital, Inc.
R1-2206414 Discussion on signaling for side control information for NR network-controlled repeaters CATT
R1-2206479 Discussion on L1/L2 signaling for side control information NEC
R1-2206598 Discussions on L1/L2 signaling for side control information Intel Corporation
R1-2206657 Discussion on L1/L2 signalling for side control information Xiaomi
R1-2206699 Discussion on L1/L2 signaling for side control information China Telecom
R1-2206841 L1/L2 signaling for side control information Samsung
R1-2206858 Discussion on ON-OFF information for NCR KT Corp.
R1-2206928 Discussion on L1/L2 signaling for side control information CMCC
R1-2206958 Discussion on L1/L2 signaling for side control information ETRI
R1-2206982 L1/L2 control signaling for enabling network controlled repeaters MediaTek Inc.
R1-2207076 Discussion on L1/L2 signaling for side control information for NCR CEWiT, IITK
R1-2207089 Discussion on L1/L2 signaling for side control information of network-controlled repeaters Lenovo
R1-2207121 Discussion on signaling for side control information Rakuten Mobile, Inc
R1-2207248 On L1/L2 signaling for side control information for NCR Qualcomm Incorporated
R1-2207346 Discussion on L1/L2 signaling for side control information Apple
R1-2207367 Discussion on L1/L2 signaling for side control information LG Electronics
R1-2207421 Discussion on L1/L2 signaling for side control information NTT DOCOMO, INC.
R1-2207681 Signaling of control information for NCR Ericsson
R1-2207848 Summary#1 on L1/L2 signaling for side control information Moderator (Fujitsu)
From Monday session
Agreement:
Beam index is used to indicate an access link beam (Option 1).
R1-2207984 Summary#2 on L1/L2 signaling for side control information Moderator (Fujitsu)
From Wed session
Agreement:
Both slot-level and symbol-level granularity are recommended for the time-domain resource indication and determination of the access link beam.
Agreement:
Both dynamic beam indication and semi-static beam indication are recommended for access link.
· Note: the semi-static beam indication includes the semi-persistent indication.
Working Assumption
In access link, a DL beam and a UL beam which are correspondent with each other have the same beam index.
Agreement:
Update the agreement achieved in RAN1#109e as follows:
For the signaling of the side control
information of timing to align transmission / reception boundaries, new
signaling may be
is unnecessary.
R1-2208110 Summary#3 on L1/L2 signaling for side control information Moderator (Fujitsu)
Agreement
In case that adaptive beams are adopted for C-link and backhaul link, the following mechanisms can be considered for the indication and determination of beams of backhaul link:
Please refer to RP-222673 for detailed scope of the WI.
R1-2208690 Work plan for NR network-controlled repeaters ZTE
R1-2208422 Side control information and behaviors for network-controlled repeaters Huawei, HiSilicon
R1-2208563 Discussion on side control information and NCR behavior Spreadtrum Communications
R1-2208656 Discussion on side control information and NCR behavior vivo
R1-2208684 Discussions on side control information for NR network-controlled repeaters InterDigital, Inc.
R1-2208691 Discussion on side control information for NCR ZTE
R1-2208778 Discussion on side control information and NCR behavior China Telecom
R1-2208989 Discussion on side control information and NCR behavior CATT
R1-2209018 Discussion on side control information and NCR behavior Fujitsu
R1-2209065 Discussion on Side control information and NCR behaviour Intel Corporation
R1-2209086 Discussion on side control information and NCR behavior Nokia, Nokia Shanghai Bell
R1-2209089 Signalling support for NR network-controlled repeaters AT&T, FirstNet
R1-2209110 Considerations on side control information and NCR behaviour Sony
R1-2209154 Discussion on side control information to enable NR network-controlled repeaters NEC
R1-2209238 Discussion on side control information and NCR behavior CAICT
R1-2209297 Discussion on side control information and NCR behavior xiaomi
R1-2209350 Discussion on side control information and NCR behavior CMCC
R1-2209378 Discussion on side control information and NCR behavior Panasonic
R1-2209408 Discussion on side control information for network-controlled repeater ETRI
R1-2209511 Side control information and NCR behavior MediaTek Inc.
R1-2209593 On side control information and NCR behavior Apple
R1-2209664 Side control information and configuration for NCR behavior Sharp
R1-2209744 Discussion on side control information and NCR behavior Samsung
R1-2209763 Discussion on UL-DL timing alignment in NCR-Fwd Rakuten Mobile, Inc
R1-2209811 Discussion on side control information and NCR behavior LG Electronics
R1-2209915 Discussion on Side control information and NCR behavior NTT DOCOMO, INC.
R1-2209998 On side control information and NCR behavior Qualcomm Incorporated
R1-2210022 Discussion on side control information and NCR behaviour Lenovo
R1-2210068 Discussion on side control information and NCR behavior KDDI Corporation
R1-2210114 Discussion on signaling side control information and NCR behavior CEWiT, IITK
R1-2210231 Side-control information and behavior in NCR Ericsson
[110bis-e-R18-Repeater-01] – Nan (ZTE)
Email discussion on side control information by October 19
- Check points: October 14, October 19
R1-2210364 Summary#1 of discussion on side control information Moderator (ZTE)
Presented in Oct 10th GTW session
R1-2210343 Summary#2 of discussion on side control information Moderator (ZTE)
R1-2210483 Summary#3 of discussion on side control information Moderator (ZTE)
From Oct 14th GTW session
Agreement:
The following information can be used to characterize the physical beam(s) supported by NCR-Fwd for access link:
· Number of beams supported for access link
o FFS: How to define the detailed value (e.g., per beam type)
o FFS: Whether the number of beam can be derived by beam layout
· Spatial relationship between different beams
· FFS: Beam types defined by the beam width (e.g. two types as wide beam and narrow beam type)
· FFS: Beam direction defined by the boresight of beam
· FFS: Whether/How to deliver this information to gNB
· FFS: Coverage area for each beam type
· FFS: Beam ID (via explicit or implicit means)
Agreement:
The following methods are supported for access link beam indication:
· Single beam index per indication is supported to indicate one beam.
· The indication of multiple beams in one indication is supported
o Note: The multiple beams are applied in TDMed over same frequency resource
Decision: As per email decision posted on Oct 17th,
Agreement
Confirm the WA that in access link, a DL beam and a UL beam which are correspondent with each other have the same beam index.
Agreement
The following aspects should be NCR capability:
· Simultaneous UL transmission of C-link and backhaul link
· Adaptive beam for C-link/backhaul-link
· Note-1: Fixed beam for C-link/backhaul link is default capability
· Note-2: TDMed UL transmission of C-link and backhaul link is default capability.
· FFS: How to define the capability for adaptive beam for C-link/backhaul-link
Conclusion
An NCR is not expected to perform forwarding in “OFF” state.
Agreement
For the flexible symbol based on the semi-static configuration (e.g., TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated), the default behavior of the NCR-Fwd is expected to be OFF or not forwarding over these symbols
· FFS: The behavior over these symbol if dynamic DL/UL operation is supported by NCR-MT and/or NCR-Fwd.
R1-2210484 Summary#4 of discussion on side control information Moderator (ZTE)
From Oct 18th GTW session
Agreement
Following parameters should be supported to define the time resource:
· For a periodic and/or semi-persistent configured time resource, starting time, duration per beam(s) and periodicity is needed.
· For aperiodic indication of time resource, starting time and duration per beam(s) is needed.
· FFS: The SCS for starting time, duration, and periodicity
· FFS: How to define the duration, e.g., via the length of time resource or resource index(es)
· FFS: Whether indication of starting time can be implicit (e.g., the first slot after the time to apply the received beam indication and the first OFDM symbol in the slot)
Agreement
If adaptive beams are adopted for C-link and backhaul link, new signaling is supported to indicate a beam(s) used for backhaul link from the set of beams for C-link.
· Predefined rule is used to define the beam in case there is no indication via the new signalling
o FFS: Details of the predefined rule
o FFS: Application of predefined rule for other cases
· Note: The beam(s) used for backhaul link should be from the RRC-configured list of beams for C-link.
· The new signalling, if needed, is an optional NCR capability
Decision: As per email decision posted on Oct 20th,
Agreement
For the ON/OFF information indication, at least one of following options is supported to indicate the ON state of NCR
· Alt-1: Explicit indication with dedicated field to indicate ON state
o Note: At least it’s supported when the beam indication is not applicable
· Alt-2: Implicit indication via the beam indication
· Alt-3: Indication via the time domain resource indication (i.e., the NCR is assumed to be ON over the indicated time domain resource)
R1-2208423 Configuration for side control information signalling of network-controlled repeaters Huawei, HiSilicon
R1-2208657 Discussion on other aspects of NCR vivo
R1-2208685 L1/L2 signaling for side control information of network-controlled repeaters InterDigital, Inc.
R1-2208692 Discussion on other aspects for NCR ZTE
R1-2208990 Discussion on control plane signalling and procedures for NR network-controlled repeaters CATT
R1-2209019 Discussion on control plane signaling and procedures relevant to RAN1 Fujitsu
R1-2209066 Discussions on L1/L2 signaling and configuration for side control information Intel Corporation
R1-2209087 "Discussion on other aspects including control plane signalling and procedures relevant to RAN1" Nokia, Nokia Shanghai Bell
R1-2209155 Discussion on other aspects for network-controlled repeaters NEC
R1-2209298 Discussion on other aspects of NCR xiaomi
R1-2209351 Discussion on other aspects including control plane signalling and procedures relevant to RAN1 CMCC
R1-2209409 Discussion on NCR signaling and procedures ETRI
R1-2209594 On control plane signaling and procedures for NCR Apple
R1-2209745 On signaling and procedures for network-controlled repeaters Samsung
R1-2209812 Discussion on other aspects for NCR LG Electronics
R1-2209916 Other aspects including control plane signalling and procedures relevant to RAN1 NTT DOCOMO, INC.
R1-2209999 On other NCR aspects Qualcomm Incorporated
R1-2210036 Discussion on signalling of side control information for network-controlled repeaters Lenovo
R1-2210232 Signaling, procedures and other aspects in NCR Ericsson
[110bis-e-R18-Repeater-02] – Lei (Fujitsu)
Email discussion on other aspects of NCR by October 19
- Check points: October 14, October 19
R1-2210282 Summary#1 on other aspects Moderator (Fujitsu)
From Oct 12th GTW session
Agreement:
For NCR-MT which can support adaptive beams in C link,
· Rel-15 beam indication framework can be reused.
·
Rel-17 beam indication
framework (i.e., the unified TCI) can be reused as well, if the NCR supports.
The gNB can configure the unified TCI for the NCR-MT, if the NCR-MT supports.
Agreement:
To support CSI measurement/reporting mechanisms for NCR-MT in C-link
· The necessary legacy mechanism for receiving CSI-RS is reused for NCR-MT.
· The necessary legacy mechanism for reporting CSI is reused for NCR-MT.
· FFS: The details of the necessary mechanisms will be further discussed and decided.
· Note: this does not mean all the legacy procedures for receiving CSI-RS and reporting CSI will be supported.
Decision: As per email decision posted on Oct 16th,
Agreement:
HARQ-ACK feedback for PDSCH carrying the side control information from higher layer (e.g., MAC-CE, RRC) is supported. The legacy HARQ-ACK feedback mechanism is reused.
Agreement:
PUCCH and PUSCH are supported for NCR-MT.
R1-2210463 Summary#2 on other aspects Moderator (Fujitsu)
From Oct 18th GTW session
Agreement:
The TA adjustment mechanism of legacy UEs is supported for NCR-MT in C link.
Agreement:
To support the sounding procedure for NCR-MT in C link, the necessary mechanism of legacy UE sounding procedure is supported.
· FFS: The details of the necessary mechanism of legacy UE sounding procedure.
· Note: This does not mean all legacy UE sounding procedure will be supported.
Please refer to RP-222673 for detailed scope of the WI.
[111-R18-NWC_Repeater] – Nan (ZTE)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
From AI 5
R1-2210818 LS to RAN1 on NCR-MT transmission and Beam correspondence RAN4, CMCC
R1-2212886 Summary#1 of discussion on the reply LS to RAN4 Moderator (CMCC)
R1-2212887 [Draft] Reply LS to RAN4 on NCR-MT transmission and Beam correspondence Moderator (CMCC)
Decision: The response to RAN4 in R1-2212887 is endorsed. Final LS is approved in R1-2212910.
R1-2210882 Side control information and behaviors for network-controlled repeaters Huawei, HiSilicon
R1-2211020 Discussion on side control information to enable NR network-controlled repeaters vivo
R1-2211080 Discussion on side control information and NCR behavior Fujitsu
R1-2211107 Discussion on side control information for NCR ZTE
R1-2211211 Discussion on side control information and NCR behavior CATT
R1-2211243 Discussion on side control information and NCR behavior Spreadtrum Communications
R1-2211303 Discussion on side control information and NCR behavior Nokia, Nokia Shanghai Bell
R1-2211317 Discussions on side control information and NCR behavior InterDigital, Inc.
R1-2211374 Discussion on side control information and NCR behavior xiaomi
R1-2211412 Discussion on Side control information to enable NR network-controlled repeater Intel Corporation
R1-2211533 Discussion on side control information and NCR behaviour China Telecom
R1-2211564 Discussion on side control information for network-controlled repeater ETRI
R1-2211602 Discussion on side control information and NCR behavior Panasonic
R1-2211621 Aspects of side control information and NCR behavior Sony
R1-2211693 Discussion on side control information and NCR behavior CMCC
R1-2211822 On side control information and NCR behavior Apple
R1-2211877 Side information on NCR beams and forwarding behaviors Sharp
R1-2211882 Discussion on side control information and NCR behaviour Lenovo
R1-2211927 Discussion on side control information and NCR behavior LG Electronics
R1-2211935 Signalling support for NR network-controlled repeaters AT&T
R1-2211996 Discussion on Side control information and NCR behavior NTT DOCOMO, INC.
R1-2212058 Discussion on side control information and NCR behavior Samsung
R1-2212130 On side control information and NCR behavior Qualcomm Incorporated
R1-2212244 Side control information and NCR behavior MediaTek Inc.
R1-2212286 Discussion on side control information and NCR behavior KDDI Corporation
R1-2212291 Discussion on side control information and NCR behaviour KT Corp.
R1-2212314 Discussion on side control information for NCR Rakuten Mobile, Inc
R1-2212323 Discussion on side control information and NCR behavior NICT
R1-2212344 Side-control information and NCR behavior Ericsson
R1-2212369 Discussion on side control information and NCR behaviour NEC
R1-2212430 Discussion on signaling side control information and NCR behavior CEWiT, IITK
R1-2212590 Summary#1 of discussion on side control information Moderator (ZTE)
From Nov 14th session
Agreement
The following is supported to deliver the information to characterize the supported physical beam of NCR-Fwd for access link:
Option-2: The information is informed to gNB and NCR via OAM
· Note-1: In this option, how to characterize the beam information is based on implementation (e.g., declaration from NCR vendor).
· Note-2: In this option, the beam(s) used by NCR-Fwd for access link is configured for gNB and NCR by OAM based on implementation.
o The beam index in SCI corresponds to the configured beam(s) sequentially.
Agreement
For FR2, the “ON” state of NCR-Fwd is indicated:
· Alt-2: Implicit indication via the beam indication (i.e., if there is beam indication, the NCR is assumed to be ON over the indicated time domain resource associated with corresponding beam(s))
Agreement
The semi-static beam indication for backhaul link is supported as:
R1-2212605 Summary#2 of discussion on side control information Moderator (ZTE)
From Nov 15th session
Agreement
The following pre-defined rules are applied to determine the beam for backhaul link:
· In the time domain resource with simultaneous downlink reception or uplink transmission in C-link and backhaul link, the beam of backhaul link is the same as the beam of C-link regardless whether there is beam indicated by the dedicated signal for backhaul link.
· In the time domain resource without simultaneous downlink reception or uplink transmission in C-link and backhaul link, if the NCR does not support capability with the new signalling for backhaul beam indication or if no beam is indicated for backhaul link by the dedicated signal,
o When Rel-15/16 beam indication framework is used for C-link,
§ The beam determined by QCL assumption for CORESET with the lowest ID and spatial relationship for PUCCH with lowest PUCCH resource ID in the C-link is applied for the DL and UL of backhaul link, respectively.
o When Rel-17 beam indication framework (i.e., unified TCI framework) is used for C-link, the indicated unified TCI for C-link DL and UL is applied for the DL and UL of backhaul link, respectively.
o Otherwise, the beam indicated by the dedicated signalling is applied for backhaul link.
Agreement
For FR1, the “ON” state of NCR-Fwd is indicated:
· Alt-2: Indication via the beam indication (i.e., if there is beam indication, the NCR is assumed to be ON over the indicated time domain resource associated with corresponding beam(s))
o When there is only one beam, the sole purpose of the beam indication is for indicating “ON” state of NCR-Fwd
Conclusion
For the flexible symbol based on the semi-static configuration (e.g., TDD-UL-DL-ConfigCommon, TDD-UL-DL-ConfigDedicated), the dynamic DL/UL operation of NCR-MT and NCR-Fwd is not supported in Rel-18.
Agreement
For each periodic beam indication for access link, one RRC signalling is used with the information defined by the following:
Option-2:
·
A list of X(
) forwarding resource, each is defined as {Beam index, time
resource}
·
FFS: The value of 
Each time resource is defined by {Starting slot defined as the slot offset in one period, starting symbol defined by symbol offset within the slot, duration defined by the number of symbols} with dedicated field.
· The periodicity is configured as part of the RRC signaling for periodic beam indication
o The same periodicity is assumed for all time resource(s) in one periodic beam indication.
· The reference SCS is configured as part of the RRC signaling for periodic beam indication
o The same reference SCS is assumed for all time resource(s) in one periodic beam indication.
R1-2212785 Summary#3 of discussion on side control information Moderator (ZTE)
From Nov 17th session
Agreement
For each aperiodic beam indication for access link, one DCI is used with the information defined by
Option-1:
·
fields are used to
indicate the beam information and each field refers to one beam index ;
o Note: The bitwidth of this field is determined by the number of beams used for access link.
·
fields to indicate the
time resource;
o Note: A list of time resource is pre-defined by RRC signalling. The bitwidth of this field for time resource indication is determined by the length of list.
·
FFS:
The value of
o Down-select between 
or 
.
· FFS: How to define the association between time indication and beam indication
Each time resource is defined by {Starting slot defined as the slot offset, starting symbol defined by symbol offset within the slot, duration defined by the number of symbols} with dedicated field.
Final summary in R1-2212786.
R1-2210883 Other aspects of network-controlled repeaters Huawei, HiSilicon
R1-2211021 Discussion on signaling for side control information vivo
R1-2211081 Discussion on control plane signaling and procedures relevant to RAN1 Fujitsu
R1-2211108 Discussion on other aspects for NCR ZTE
R1-2211212 Discussion on control plane signalling and procedures for NR network-controlled repeaters CATT
R1-2211304 Discussion on other aspects including control plane signalling and procedures relevant to RAN1 Nokia, Nokia Shanghai Bell
R1-2211318 Discussion on control plane signaling and procedures for network-controlled repeaters InterDigital, Inc.
R1-2211375 Discussion on other aspects of NCR xiaomi
R1-2211413 Discussions on L1/L2 signaling and configuration for side control information Intel Corporation
R1-2211511 Discussion on other aspects including control plane signalling and procedures for NCR IIT-K, CEWiT
R1-2211565 Discussion on NCR signaling and procedures ETRI
R1-2211622 Aspects of signaling and control procedures relevant to RAN1 Sony
R1-2211632 Discussion on NCR control plane signalling and procedures Panasonic
R1-2211694 Discussion on other aspects including control plane signalling and procedures relevant to RAN1 CMCC
R1-2211763 Discussion on NCR control information signalling and procedures Lenovo
R1-2211823 On control plane signaling and procedures for NCR Apple
R1-2211918 Discussion on other aspects of NCR CAICT
R1-2211928 Discussion on other aspects for NCR LG Electronics
R1-2211997 Other aspects including control plane signalling and procedures relevant to RAN1 NTT DOCOMO, INC.
R1-2212059 On signaling and procedures for network-controlled repeaters Samsung
R1-2212131 On other NCR aspects Qualcomm Incorporated
R1-2212319 Discussion on other aspects for NCR Rakuten Mobile, Inc
R1-2212345 Other aspects including control signaling and procedures in NCR Ericsson
R1-2212370 Discussion on other aspects for network-controlled repeaters NEC
R1-2212552 Summary#1 on other aspects Moderator (Fujitsu)
From Nov 14th session
Agreement
As optional functionalities for the NCR-MT, at least Rel-15 legacy BFD/BFR/RLM mechanisms are supported
· FFS: The behavior of NCR-Fwd when BFR/RLF happen in C link.
R1-2212705 Summary#2 on other aspects Moderator (Fujitsu)
From Nov 15th session
Agreement
· Legacy Rel-15 initial/random access procedure is supported for NCR-MTs in C link.
o Note: No additional enhancement is necessary from RAN1 point of view.
· The CRC bits of the PDCCHs carrying side control information are scrambled by a new dedicated RNTI
o Applicable only for NCR-MT
Please refer to RP-223505 for detailed scope of the WI.
[112-R18-NCR] – Nan (ZTE)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2300701 Discussion on RRC and MAC CE parameters for NCR ZTE
R1-2300121 Side control information and behaviors for network-controlled repeaters Huawei, HiSilicon
R1-2300232 Discussion on side control information and NCR behavior Spreadtrum Communications
R1-2300467 Discussion on side control information and NCR behavior vivo
R1-2300589 Discussion on side control information and NCR behavior xiaomi
R1-2300595 Discussions on side control information and NCR behavior InterDigital, Inc.
R1-2300694 Side control information to enable NR network-controlled repeaters CATT
R1-2300702 Discussion on side control information for NCR ZTE
R1-2300724 Discussion on side control information and NCR behavior China Telecom
R1-2300754 Discussion on side control information and NCR behavior Fujitsu
R1-2300772 Discussion on side control information and NCR behavior Nokia, Nokia Shanghai Bell
R1-2300781 NCR side control information for NCR operations Sharp
R1-2300834 Discussion on side control information and NCR behaviour NEC
R1-2300885 More considerations on side control information and NCR behavior Sony
R1-2300920 Discussion on side control information and NCR behaviour Lenovo
R1-2300962 Discussion on Side control information to enable NR network-controlled repeater Intel Corporation
R1-2301016 Discussion on side control information and NCR behavior CMCC
R1-2301036 Discussion on side control information and NCR behavior NICT
R1-2301049 Discussion on side control information for network-controlled repeater ETRI
R1-2301070 Discussion on side control information and NCR behavior LG Electronics
R1-2301099 Discussion on side control information and NCR behavior Panasonic
R1-2301136 Discussion on side control information and NCR behavior KDDI Corporation
R1-2301145 Discussion on signaling side control information and NCR behaviour IIT Kanpur, CEWiT
R1-2301278 Discussion on side control information and NCR behavior Samsung
R1-2301360 On side control information and NCR behavior Apple
R1-2301427 On side control information and NCR behavior Qualcomm Incorporated
R1-2301507 Discussion on Side control information and NCR behavior NTT DOCOMO, INC.
R1-2301617 Side control information and NCR behavior MediaTek Inc.
R1-2301766 Side-control information and NCR behavior Ericsson
R1-2301898 Summary#1 of discussion on side control information Moderator(ZTE)
From Monday session
Agreement
For each aperiodic beam indication
for access link via DCI, 
is supported.
Agreement
For aperiodic beam indication for access link, the reference SCS for the time resource is configured by RRC signalling for time resource configuration.
R1-2301899 Summary#2 of discussion on side control information Moderator(ZTE)
From Tuesday morning
Agreement
For semi-persistent beam indication:
list of
forwarding resource, the 
th list is consist
of 
forwarding
resources, and each forwarding resource is defined by {beam index, time
resource}. § The periodicity and reference SCS is configured as part of the RRC signaling for each list of forwarding resource
forwarding
resources in this list are selected. 
(
) is
128, where refers
to the maximum beams indicated in one indication.
R1-2302034 Summary#3 of discussion on side control information Moderator (ZTE)
From Wednesday session
Agreement
For aperiodic beam indication, the bitwidth of each field for beam indication in DCI is explicitly configured by dedicated RRC.
Agreement
A priority flag is introduced per list of periodic and semi-persistent indications. The flag gives priority to periodic and semi-persistent indications over aperiodic indications. Additionally, the following applies:
· If there is conflict among beam indication from different type of indication, the order of priority is defined as: Aperiodic beam indication > semi-persistent beam indication > periodic beam indication.
o No conflict is expected between periodic beam indications
o No conflict is expected between semi-persistent indications
o If there is conflict between two aperiodic indications, the latest indication is prioritized.
Agreement
In the time domain resource without simultaneous downlink reception or uplink transmission in C-link and backhaul link, if the NCR does not support capability with the new signalling for backhaul beam indication or if no beam is indicated for backhaul link by the dedicated signal,
o If no unified TCI is applied for C-link, the beam determined by QCL assumption for CORESET with the lowest ID and spatial relationship for PUCCH with lowest PUCCH resource ID in the C-link is applied for the DL and UL of backhaul link, respectively. (i.e. same as the default beam defined for Rel-15/16 beam indication framework)
R1-2302035 Summary#4 of discussion on side control information Moderator (ZTE)
From Friday session
R1-2302113 LS to RAN2 on the RRC and MAC CE parameters for NCR RAN1, ZTE
Agreement
The RRC parameters and MAC CE parameters in R1-2302113 are agreed. LS to RAN2 is approved in R1-2302227.
Agreement
For the semi-persistent beam
indication, the indicated information should be
applied starting from the first slot that is after slot 
, where n refers to the
slot that NCR-MT would transmit HARQ-ACK information corresponding
to the PDSCH carrying the activation command and 
is the SCS
configuration for the channel carrying the HARQ-ACK information.
Agreement
For the aperiodic beam indication, the reference of slot offset for each time resource is defined as the slot n+k where n refers to the slot that NCR-MT receive the DCI carrying the indication and:
Agreement
Update the agreements on ‘ON-OFF’ achieved in RAN1 #111 as follows:
|
For FR2, the “ON” state of NCR-Fwd is indicated: · Implicit indication via the AC link beam indication (i.e., if there is an AC link beam indication, the NCR is assumed to be ON over the indicated time domain resource associated with corresponding beam(s)) For FR1, the “ON” state of NCR-Fwd is indicated: · Indication via the AC link beam indication (i.e., if there is an AC link beam indication, the NCR is assumed to be ON over the indicated time domain resource associated with corresponding beam(s)) o When there is only one beam, the sole purpose of the AC link beam indication is for indicating “ON” state of NCR-Fwd Note: Backhaul link is following the AC link in terms of ON/OFF |
Agreement
The DCI Format 5_0 carrying the side control information is monitored by the NCR-MT at least in the UE specific search space.
Agreement
For periodic and semi-persistent beam indication,
For periodic beam indication,
The maximum number of forwarding resources in one periodic beam indication is 1024.
Agreement
For aperiodic beam indication,
R1-2300122 Other aspects of network-controlled repeaters Huawei, HiSilicon
R1-2300468 Discussion on other aspects of NCR vivo
R1-2300590 Discussion on other aspects of NCR xiaomi
R1-2300596 Discussion on control plane signaling and procedures for network-controlled repeaters InterDigital, Inc.
R1-2300695 Discussion on signaling for side control information for NR network-controlled repeaters CATT
R1-2300703 Discussion on other aspects for NCR ZTE
R1-2300755 Discussion on control plane signaling and procedures relevant to RAN1 Fujitsu
R1-2300773 Discussion on other aspects including control plane signalling and procedures relevant to RAN1 Nokia, Nokia Shanghai Bell
R1-2300835 Discussion on other aspects for network-controlled repeaters NEC
R1-2300886 More considerations on signaling and control procedures relevant to RAN1 Sony
R1-2300963 Discussions on other aspects including control plane signaling and procedures Intel Corporation
R1-2301017 Discussion on other including control plane signalling and procedures CMCC
R1-2301038 Discussion on other aspects of NCR CAICT
R1-2301050 Discussion on NCR signaling and procedures ETRI
R1-2301071 Discussion on other aspects for NCR LG Electronics
R1-2301279 On signaling and procedures for network-controlled repeaters Samsung
R1-2301361 On control plane signaling and procedures for NCR Apple
R1-2301428 On other NCR aspects Qualcomm Incorporated
R1-2301508 Other aspects including control plane signalling and procedures relevant to RAN1 NTT DOCOMO, INC.
R1-2301637 Discussion on NCR control plane signaling and procedures Lenovo
R1-2301767 Other aspects including control signaling and procedures for NCR Ericsson
R1-2301832 Summary#1 on other aspects Moderator (Fujitsu)
From Tuesday session
Agreement
Once a beam failure is detected in C
link by NCR-MT, NCR-Fwd is OFF until the beam failure is recovered
recovery is completed.
[114bis-R18-NCR] – Nan (ZTE)
Email discussion on NR network controlled repeaters
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2308905 Maintenance of side control information and NCR behaviour Huawei, HiSilicon
R1-2309088 Remaining issues on side control information and NCR behaviour vivo
R1-2309147 Remaining issue on side control information and NCR behavior ZTE
R1-2309331 Remaining issues on side control information and NCR behaviour LG Electronics
R1-2309389 Remaining Issues on side control information and NCR behaviour Samsung
R1-2309431 Discussion on remaining issues of NCR xiaomi
R1-2309500 Maintenance on side control information and NCR behaviour for NR Network-Controlled Repeaters CATT
R1-2309542 Remaining issues for side control information and NCR behaviour InterDigital, Inc.
R1-2309641 Remaining issues on side control information and NCR behaviour Fujitsu
R1-2309684 Remaining issues on side control information and NCR behaviour CMCC
R1-2309708 Discussion on NCR maintenance ETRI
R1-2309774 Side-control information and NCR behaviour Ericsson
R1-2309792 Discussion on remaining issues of side control information for NCR Lenovo
R1-2310046 Discussion on Side control information and NCR behavior NTT DOCOMO, INC.
R1-2310413 Summary#1 of maintenance issues on side control information and NCR behavior Moderator (ZTE)
From Tuesday session
Agreement
For the aperiodic beam indication, to determine the reference of slot offset for each time resource, the SCS for k is same as the SCS for PDCCH.
Agreement
The Periodic beam indication with priority flag has higher priority than semi-persistent beam indication without priority flag.
Agreement
The following TP for 38.213 clause 20 is accepted:
|
When the NCR does not simultaneously receive on the control link and the backhaul link - if the NCR does not support determination of a TCI state for receptions on the backhaul link based on an indication of a TCI state by the serving cell, or if the NCR does not receive an indication of a TCI state, for receptions on the backhaul link [11, TS 38.321] - if the NCR does not receive an indication of a unified TCI state for receptions by the NCR-MT, receptions on the backhaul link use same QCL parameters as the ones for PDCCH receptions in a CORESET with the lowest controlResourceSetId in the active DL BWP - else, receptions on the backhaul link use the QCL parameters provided by an indicated unified TCI state for receptions by the NCR-MT - else receptions on the backhaul link use QCL parameters provided by a TCI state in a MAC CE [11, TS 38.321]. When the NCR does not simultaneously transmit on the control link and the backhaul link - if the NCR does not support determination of a spatial filter for transmissions on the backhaul link based on an indication of a unified TCI state or SRI by the serving cell, or if the NCR-MT does not receive an indication of a unified TCI state or SRI for determining a spatial filter, for transmissions on the backhaul link - if the NCR does not receive an indication of a unified TCI state for transmissions by the NCR-MT, transmissions on the backhaul link use a same spatial filter as the one associated with the PUCCH resource with the smallest pucch-ResourceId in PUCCH-ResourceSet in the active UL BWP - else, transmissions on the backhaul link use a spatial filter corresponding to an indicated unified TCI state for transmissions by the NCR-MT. - else transmissions on the backhaul link use a spatial filter corresponding to a unified TCI state or SRI provided by a MAC CE [11, TS 38.321]. If the NCR receives an indication of a TCI state for receptions on
the backhaul link in a MAC CE command or an indication of a unified TCI state
or SRI for determining a spatial filter for transmissions on the backhaul
link in a MAC CE command, the NCR applies the MAC CE command from the first
slot that is after slot |
Agreement
The following TP for 38.213 clause 20 is accepted:
|
The
NCR-Fwd uses |
R1-2310494 Summary#2 of maintenance issues on side control information and NCR behavior Moderator (ZTE)
From Thursday session
Agreement
The reference slot determined by the configured SCS (ncr-referenceSCS) is the first slot that starts no earlier than the start of slot n+k in the numerology of the PDCCH in which the indication is received.
· The following TP for 38.213 clause 20 is endorsed.
|
Reason for change: In the current specification, it is not clear what the SCSs for slot n of the PDCCH reception, offset value k in FG 43-3 and the reference slot for time resources are. The specification also does not consider how to determine the reference slot for time resources if the SCS of the PDCCH and the reference SCS provided by ncr-referenceSCS for the NCR-Fwd are different. Summary of change: Clarify the SCSs for slot n of the PDCCH reception, offset value k in FG 43-3 and the reference slot for time resources, and define the reference slot based on the slot n of the PDCCH reception and offset value k. Consequences if not approved: The SCSs for slot n of the PDCCH reception, offset value k in FG 43-3 and the reference slot for time resources are not clear. ========================================================================= < Unchanged text omitted > The NCR-MT can be configured to monitor PDCCH according to USS sets for detection of a DCI format 2_8 with CRC scrambled by an NCR-RNTI. A time resource and a corresponding beam index for transmissions or receptions on the access link are indicated by corresponding fields in DCI format 2_8 [4, TS 38.212]. When the NCR detects more than one DCI formats 2_8 that indicate beam indexes for time resources overlapping in a set of symbols, the NCR uses for the set of symbols a beam index that is indicated by a DCI format 2_8 that the NCR-MT detects in a most recent PDCCH monitoring occasion. The time resource starts at a slot that is offset by slotOffsetAperiodic slots from a reference slot and at a symbol that is offset by symbolOffset from the start of the slot, and has a duration provided by durationInSymbols for a SCS provided by ncr-referenceSCS. The reference slot is the first slot with the SCS provided by ncr-referenceSCS that starts no earlier than the start of a slot that is after a slot of a PDCCH reception that provides the DCI format 2_8 by a number of slots indicated by FG 43-3 with the SCS of PDCCH reception. < Unchanged text omitted > |
Agreement
· The following TP for 38.213 clause 20 is accepted:
|
Reason for change: To capture the agreement made in RAN1#104-b to address the remaining issue for priority between beam indications. Summary of change: Clarify the Periodic beam indication with priority flag has higher priority than semi-persistent beam indication without priority flag. Consequences if not approved: Without this change, it will be an error case if conflict beam indication occurs. ========================================================================= 20 Network controlled repeater *** Unchanged parts are omitted *** If - a first time resource provided by NCR-SemiPersistentFwdResourceSet is indicated by a MAC CE command and is associated with a first beam index, and - a second time resource is provided by NCR-PeriodicFwdResourceSet and is associated with a second beam index, and - the first time resource overlaps with the second time resource in a set of symbols, the NCR applies the first beam index for transmissions or receptions on the access link in the set of symbols unless only the NCR-PeriodicFwdResourceSet includes a priorityFlag, in which case the second beam index is applied. *** Unchanged parts are omitted *** |
Agreement
If an NCR does not support simultaneous transmission on C-link and backhaul link, NCR-Fwd does not transmit over the time resource if NCR-MT transmits on the same time resource.
Conclusion
There is no consensus to have enhancement on the DCI size of DCI 2-8 to satisfy the “DCI size budget”. It is up to gNB to ensure “3+1” DCI size budget.
R1-2308906 Maintenance of other aspects for NCR Huawei, HiSilicon
R1-2309148 Remaining issue on other aspects of NCR ZTE
R1-2309390 Remaining Issues on signaling and procedures for network-controlled repeaters Samsung
R1-2309501 Maintenance on other aspects including control plane signalling and procedures relevant to RAN1 for NR Network-Controlled Repeaters CATT
R1-2309775 Control-plane signaling and procedures for NCR Ericsson
R1-2309846 On remaining issues for BFR procedures for backhaul link in NCR Apple
R1-2310311 Summary#1 on other aspects Moderator (Fujitsu)
From Tuesday session
Agreement
· Accept following TP.
----------------------------------------Start of TP#1 for TS 38.211 Clause 3.3 & Clause 4.1 -----------------------------------------
< Unchanged text omitted >
3.3 Abbreviations
IAB-MT IAB mobile termination
IE Information element
NCR-MT Network controlled repeater - mobile termination
PBCH Physical broadcast channel
< Unchanged text omitted >
4.1 General
Throughout
this specification, unless otherwise noted, the size of various fields in the
time domain is expressed in time units 
where 
Hz and 
. The
constant 
where
, 
and 
.
Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4, 5, 6, or 7 are equally applicable to the IAB-MT part of an IAB-node and the NCR-MT part of an NCR node.
< Unchanged text omitted >
--------------------------------------------------------------End of TP#1---------------------------------------------------------------------
Agreement
· Accept following TP.
----------------------------------------Start of TP#2 for TS 38.214 Clause 3.3 & Clause 4 --------------------------------------------
< Unchanged text omitted >
3.3 Abbreviations
IAB-MT Integrated Access and Backhaul – Mobile Terminal
L1-RSRP Layer 1 reference signal received power
LI Layer Indicator
MCS Modulation and coding scheme
NCR-MT Network controlled repeater - mobile termination
PDCCH Physical downlink control channel
< Unchanged text omitted >
4 Power control
Throughout this specification, unless otherwise noted, statements using the term "UE" in clauses 4, 5, or 6 are equally applicable to the IAB-MT part of an IAB node and the NCR-MT part of an NCR node.
< Unchanged text omitted >
--------------------------------------------------------------End of TP#2---------------------------------------------------------------------
[115-R18-NCR] – Nan (ZTE)
Email discussion on NR network controlled repeaters
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2312671 List of agreements on NCR in RAN1#115 ZTE
R1-2310860 Maintenance of side control information and NCR behaviour Huawei, HiSilicon
R1-2311030 Side-control information and NCR behaviour Ericsson
R1-2311045 Remaining issues on side control information and NCR behaviour Fujitsu
R1-2311128 Discussion on side control information and NCR behavior Nokia, Nokia Shanghai Bell
R1-2311176 Remaining issue on side control information and NCR behavior Spreadtrum Communications
R1-2311197 Remaining issue on side control information and NCR behavior ZTE
R1-2311282 Maintenance on side control information and NCR behavior Panasonic
R1-2311321 Maintenance on side control information and NCR behaviour for NR Network-Controlled Repeaters CATT
R1-2311386 Discussion on remaining issues of NCR xiaomi
R1-2311495 Remaining issues on side control information and NCR behaviour CMCC
R1-2311551 Remaining issues on side control information and NCR behaviour China Telecom
R1-2311697 On remaining issues for side control information for NCR Apple
R1-2311757 Discussion on NCR maintenance ETRI
R1-2311858 Remaining Issues on side control information and NCR behaviour Samsung
R1-2311917 Remaining issues on side control information and NCR behaviour LG Electronics
R1-2312375 Summary#1 of maintenance issues on side control information and NCR behavior Moderator (ZTE)
From Tuesday session
Agreement
For the timing determination of backhaul link:
· The Fwd’s backhaul link DL/UL timing follows the MT’s DL/UL frame timing.
Agreement
|
Reason for change: Adding the missing abbreviation of NCR. Summary of change: The abbreviation of NCR is added. Consequences if not approved: The abbreviation in 38.212 is incomplete. ==================================================================================== *** Unchanged parts are omitted *** 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. *** Unchanged parts are omitted *** MBS Multicast Broadcast Services MCS Modulation and Coding Scheme NCR Network-controlled repeater OFDM Orthogonal Frequency Division Multiplex PBCH Physical Broadcast Channel *** Unchanged parts are omitted *** |
Agreement
|
Reason for change: The determination of NCR-Fwd’s timing is missing in the spec. Summary of change: Add an additional description to reflect the relevant agreement in current text proposal. Consequences if not approved: The determination of timing line for forwarding may not be clear. ==================================================================================== <omitted part> If - a first time resource provided by NCR-SemiPersistentFwdResourceSet is indicated by the NCR Access Link Beam Indication MAC CE command and is associated with a first beam index, and - a second time resource is provided by NCR-PeriodicFwdResourceSet and is associated with a second beam index, and - the first time resource overlaps with the second time resource in a set of symbols, the NCR applies, for transmissions or receptions on the access link in the set of symbols, the second beam index if only NCR-PeriodicFwdResourceSet includes priorityFlag, and the first beam index otherwise. If - a first time resource is provided by NCR-PeriodicFwdResourceSet or NCR-SemiPersistentFwdResourceSet with indication by the NCR Access Link Beam Indication MAC CE command and is associated with a first beam index, and - a second time resource is indicated by DCI format 2_8 and is associated with a second beam index provided by the DCI format 2_8, and - the first time resource overlaps with the second time resource in a set of symbols, the NCR applies, for transmissions or receptions on the access link in the set of symbols, - the first beam index if NCR-PeriodicFwdResourceSet or NCR-SemiPersistentFwdResourceSet includes priorityFlag, and - the second beam index if NCR-PeriodicFwdResourceSet or NCR-SemiPersistentFwdResourceSet does not include priorityFlag. <omitted part> |
R1-2312535 Summary#2 of maintenance issues on side control information and NCR behavior Moderator (ZTE)
From Thursday session
Agreement
The same CP of the active BWP of control link is assumed to determine the symbol length for the configured time resource.
|
Reason for change: The CP type of time resource for access link is not specified. There are two CP type in NR: Normal CP and Extended CP. For different CP type, the number of symbols in one slot and the length of symbol are different. So, clarification on the assumption of CP type is needed for time resource configuration. Summary of change: Add a sentence “and the cyclicPrefix of the active BWP.” in current text proposal. Consequences if not approved: If the NCR does not know the CP type of time resource for access link, the number of symbols in one slot and the length of symbol of time resource for access link are unclear.
20 Network controlled repeater < Unchanged parts are omitted> The NCR can be provided by ncr-PeriodicFwdResourceSetToAddModList a list of sets of resources for transmissions or receptions on the access link. A set of resources, from the list of sets of resources, is provided by NCR-PeriodicFwdResourceSet and occurs with a periodicity provided by ncr-periodicity. A resource from the set of resources is provided by NCR-PeriodicFwdResource and includes a pair of a time resource provided by ncr-PeriodicTimeResource and a beam [20, TS 38.106] with an index provided by ncr-beamIndex. The time resource starts at a slot that is offset by slotOffsetPeriodic slots from the start of the period for the set of resources and at a symbol that is offset by symbolOffset from the start of the slot, and has a duration provided by durationInSymbols for a SCS provided by ncr-referenceSCS and the cyclicPrefix of the active BWP. The
NCR can be provided by ncr-SemiPersistentFwdResourceSetToAddModList a
list of sets of resources for transmissions or receptions on the access link
and a MAC CE command can indicate a set of resources for the NCR to use or to
stop using based on a corresponding identity provided by ncr-SemiPersistentFwdResourceSetId
[11, TS 38.321]. The NCR uses or stops using the set of resources starting
from the first slot that is after slot The NCR-MT can be configured to monitor PDCCH according to USS sets for detection of a DCI format 2_8 with CRC scrambled by an NCR-RNTI. A time resource and a corresponding beam index for transmissions or receptions on the access link are indicated by corresponding fields in DCI format 2_8 [4, TS 38.212]. When the NCR detects more than one DCI formats 2_8 that indicate beam indexes for time resources overlapping in a set of symbols, the NCR uses for the set of symbols a beam index that is indicated by a DCI format 2_8 that the NCR-MT detects in a most recent PDCCH monitoring occasion. The time resource starts at a slot that is offset by slotOffsetAperiodic slots from a reference slot and at a symbol that is offset by symbolOffset from the start of the slot, and has a duration provided by durationInSymbols for a SCS provided by ncr-referenceSCS and the cyclicPrefix of the active BWP.The reference slot is a slot that is after a slot of a PDCCH reception that provides the DCI format 2_8 by a number of slots indicated by FG 43-3. < Unchanged parts are omitted > |
Conclusion
For BH-link beam indication via dedicated
MAC-CE, when an active BWP of the C-link is switched, the BH-link beam
determined by the last MAC CE before BWP switching is used until the application of the beam
indicated by a new MAC-CE received in
the active BWP.
Note: No spec impact is needed.
R1-2310861 Maintenance of other aspects for NCR Huawei, HiSilicon
R1-2311031 Control-plane signaling and procedures for NCR Ericsson
R1-2311129 Discussion on other aspects including control plane signalling and procedures relevant to RAN1 Nokia, Nokia Shanghai Bell
R1-2311198 Remaining issue on other aspects of NCR ZTE
R1-2311322 Maintenance on other aspects including control plane signalling and procedures relevant to RAN1 for NR Network-Controlled Repeaters CATT
R1-2311859 Remaining Issues on signaling and procedures for network-controlled repeaters Samsung
R1-2312307 Summary#1 on other aspects Moderator (Fujitsu)
From Tuesday session
Agreement
----------------------------------------Start of TP#1 for TS 38.212 Clause 7.3.1.3.9 -----------------------------------------
< Unchanged parts are omitted>
7.3.1.3.9 Format 2_8
DCI format 2_8 is used for notifying the aperiodic beam indication and associated time resources
The following information is transmitted by means of the DCI format 2_8 with CRC scrambled by NCR-RNTI:
- Beam index 1, Beam index 2, …, Beam index N
The bitwidth
of each beam index field is determined by the higher layer parameter ncr-AperiodicBeamFieldWidth aperiodicBeamFieldWidth.
- Time resource indication 1, Time resource indication 2, …, Time resource indication N
The bitwidth
of each time
resource indication field is determined by max
, where 
is the
number of time domain resources configured by ncr-AperiodicFwdConfig aperiodicFwdConfig. The bit field indexes of
a time resource indication field are mapped to the time domain resources
configured by ncr-AperiodicFwdConfig aperiodicFwdConfig according to an ascending
order of a resource identity configured by ncr-AperiodicFwdTimeResourceId aperiodicFwdTimeRsrcId, with the
bit field index 0 mapped to the time resource with the smallest resource
identity.
The N beam indexes are sequentially associated with the N time resource indications with one to one mapping. N is configured by the higher layer parameter numberOfFields. The size of DCI format 2_8 is up to 128 bits.
< Unchanged parts are omitted>
--------------------------------------------------------------End of TP#1-------------------------------------------------------------------
R1-2401762 Session notes for 8.7 (Maintenance on NR Network-Controlled Repeaters) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
[116-R18-NCR] – Nan (ZTE)
Email discussion on NR network controlled repeaters
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2400151 Maintenance on NR Network-Controlled Repeaters Huawei, HiSilicon
R1-2400351 Remaining issue on side control information and NCR behavior ZTE
R1-2400412 Maintenance on NR Network-Controlled Repeaters CATT
R1-2400462 Maintenance on side control information and behaviour for NCR NEC
R1-2400650 Discussion on Maintenance on NR Network-Controlled Repeaters Nokia, Nokia Shanghai Bell
R1-2400705 Maintenance on NR Network-Controlled Repeaters Samsung
R1-2401241 Maintenance on NR Network-controlled Repeaters Ericsson
R1-2401651 Summary#1 of maintenance issues on side control information and NCR behavior Moderator (ZTE)
From Wednesday session
Conclusion
No specification impact for power sharing across NCR-MT and NCR-Fwd for simultaneous UL transmission in Rel-18.
Agreement
No conflict on the AP-beam indication is expected over the overlapped time resources indicated in a single DCI.
Agreement
· Adopt the following TP for TS 38.213 for alignment.
|
Reason for change: In TS 38.213, for access link beam indication, the capability name AperiodicBeamIndicationForAccessLink is not aligned with ncr-AperiodicBeamInd-AccessLink in TS 38.306. Summary of change: In TS38.213, Section 20, “AperiodicBeamIndicationForAccessLink” is changed to “ncr-AperiodicBeamInd-AccessLink”. Consequences if not approved: The parameter name is not aligned in TS 38.213 and TS 38.306.
< Unchanged text omitted > 20 Network controlled repeater The NCR-MT can be
configured to monitor PDCCH according to USS sets for detection of a DCI
format 2_8
with CRC scrambled by an NCR-RNTI. A time resource and a corresponding beam
index for transmissions or receptions on the access link are indicated by
corresponding fields in DCI format 2_8 [4, TS 38.212]. When the NCR detects
more than one DCI formats 2_8 that indicate beam indexes for time resources
overlapping in a set of symbols, the NCR uses for the set of symbols a beam
index that is indicated by a DCI format 2_8 that the NCR-MT detects in a most
recent PDCCH monitoring occasion. The time resource starts at a slot that is
offset by slotOffsetAperiodic slots from a reference slot and at a
symbol that is offset by symbolOffset from the start of the slot, and
has a duration provided by durationInSymbols for a SCS provided by referenceSCS
and the cyclicPrefix of the active DL BWP. The reference slot is the first
slot with the SCS provided by referenceSCS that starts no
earlier than the start of a slot that is after a slot of a PDCCH
reception that provides the DCI format 2_8 by a number of slots indicated by < Unchanged text omitted > |
